Open topic with navigation

Code Review

Code Review iCube enables users to create ad-hoc reports to understand the code review cycle. Using this iCube, project executives will be able to get insights into time taken for code reviews. It also helps in keeping track of the code changes.

Note: This iCube supports Bitbucket and GitLab source system.

Attributes

Expand this link to view the list of attributes available as part of the Code Review iCube:

Attribute	Description
Branch Name	Name of the branch on which pull request is initiated
Calendar Date	Gregorian calendar date displayed in the format 'M/D/YYYY'
Calendar Month	Gregorian calendar month displayed in the format 'Mon YYYY'
Calendar Quarter	Gregorian calendar quarter displayed in the format 'Q# YYYY'
Calendar Week	Gregorian calendar week displaying the week number. For example, W21, W22.
Calendar Year	Gregorian calendar year displayed in the format YYYY
Date	The date on which the code was committed
First Reaction Date	The earliest date on which a reviewer gave reaction for a PR
Project Name	Name of the project to which code is being developed
Pull Request ID	ID for the pull request
Pull Request Reviewer	Name of the reviewer for the pull request
Repository Name	Name of the repository which holds the code

Metrics

Expand this link to view the list of metrics available as part of the Code Review iCube:

Metric	Description	Formula/Condition	Expected Value
Time to First Reaction (Hours)	Duration from when the pull request was created to the time when the reviewer first reacted	[Time to First Reaction] / 3600	Closer to 0 is ideal
Response Count	Indicative of the response of the reviewer	Case(IsNull([Time to First Reaction (Hours)]), 0, 1)	1 or 0